Methods and systems for bulk uploading of data in an on-demand service environment

ABSTRACT

Methods and systems for bulk uploading of data in an on-demand service environment are described. In one embodiment, such a method includes retrieving a bulk transaction request from a transaction queue within a host organization, where the bulk transaction request specifies a plurality of database transactions to be processed against a multi-tenant database system of the host organization. Such a method further includes determining a current computational load of the multi-tenant database system, processing a subset of the plurality of database transactions specified by the bulk transaction request against the multi-tenant database system when the current computational load is below a threshold, and updating a bulk transaction results log based on the subset of the plurality of database transactions processed. Remaining database transactions specified by the bulk transaction request may then be re-queued for later processing.

CLAIM OF PRIORITY

This application is a divisional of the utility application entitled“METHODS AND SYSTEMS FOR BULK UPLOADING OF DATA IN AN ON-DEMAND SERVICEENVIRONMENT,” filed on Feb. 24, 2015, having an application number ofSer. No. 14/630,567, which is a divisional application of, and claimspriority to, the utility application entitled “METHODS AND SYSTEMS FORBULK UPLOADING OF DATA IN AN ON-DEMAND SERVICE ENVIRONMENT,” filed onDec. 20, 2010, having an application number of Ser. No. 12/973,687; andthe provisional utility application entitled “METHODS AND SYSTEMS FORBULK UPLOADING OF DATA IN AN ON-DEMAND SERVICE ENVIRONMENT,” filed onApr. 1, 2010, having an application number of 61/320,189, the entirecontents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The subject matter described herein relates generally to the field ofcomputing, and more particularly, to methods and systems for bulkuploading of data in an on-demand service environment.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also correspond toembodiments of the claimed subject matter.

In a conventional client/server transaction a client computing devicesubmits a request to a server, the server processes the request, andthen returns a result to the client, thus completing the transactioncycle. While such a model works well for simple transactions thatprocess quickly, the above model does not scale well to transactionsthat require longer durations to process. One problem is that a clientdevice awaiting a response from a server may appear to have “hung” or“crashed” while awaiting the response, or may simply time out, before aresponse is received, thus having wasted the period of time awaiting aserver response, and potentially having caused a server to wasteresources developing a response that is never received by the client.

Although a result from the server may eventually be forthcoming, aclient experiencing a perceived delay may terminate prematurely andpotentially re-submit the request, causing duplicative effort on thepart of the server and potentially introducing transactional errors,such as having the server implement the same request multiple times.

Such a problem is exacerbated where a client device is attempting toupload a large amount of data to a database or initiate a large numberof transactions with a database. Undesirable data inconsistencies mayoccur where a client terminates prematurely or times out without havingreceived a response from the server, especially where the client thenre-submits the same request.

The present state of the art may therefore benefit from the methods andsystems for bulk uploading of data in an on-demand service environmentas described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example, and not by way oflimitation, and can be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 illustrates an exemplary architecture in which embodiments mayoperate;

FIG. 2 illustrates an alternative exemplary architecture in whichembodiments may operate;

FIG. 3 shows a diagrammatic representation of a system in whichembodiments may operate, be installed, integrated, or configured;

FIG. 4 is a flow diagram illustrating a method for bulk uploading ofdata in an on-demand service environment in accordance with oneembodiment; and

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system, in accordance with one embodiment.

DETAILED DESCRIPTION

Described herein are systems, devices, and methods for bulk uploading ofdata in an on-demand service environment. In one embodiment, such amethod includes retrieving a bulk transaction request from a transactionqueue within a host organization, where the bulk transaction requestspecifies a plurality of database transactions to be processed against amulti-tenant database system of the host organization. Such a methodfurther includes determining a current computational load of themulti-tenant database system, processing a subset of the plurality ofdatabase transactions specified by the bulk transaction request againstthe multi-tenant database system when the current computational load isbelow a threshold, and updating a bulk transaction results log based onthe subset of the plurality of database transactions processed.Remaining database transactions specified by the bulk transactionrequest may then be re-queued for later processing.

For example, in an on-demand service environment, such as a “cloudcomputing” environment where a host organization provides computingresources and services to customer organizations, customer organizationsmay transact with the host organization by way of a client request and aserver response cycle. In such a cycle, the client sends a request, andawaits a response from the server before proceeding to another task. Forexample, the client may submit a database transaction, such as a recordadd, a record retrieval, a record update, a record search, and so forth,and simply await the response from the server. This type of transactioncycle, where the client device awaits a response from the server issometimes referred to as synchronous processing.

However, customer organizations utilizing such services may find itnecessary to upload large amounts of data to the host organization, thusmaking the synchronous client/server request/response model undesirable.

Take for example a customer organization needing to upload a largenumber of records (e.g., thousands, tens of thousands, or hundreds ofthousands of records, etc.) to a database provided by the hostorganization. Such a need may arise where a customer organization ismigrating their locally implemented database to the cloud (e.g., to theon-demand service provided by the host organization); where the customerorganization is uploading locally transacted but non-synced records tothe on-demand service for the purposes of creating a live backupresource in the cloud (e.g., via the host organization) for redundancyor for overflow processing, etc.

Various problems arise where a customer organization attempts to submitall the data associated with a large request as a single request whenusing synchronous processing. For example, such a request may exceed anallowable transfer data limit inherent to an http (hyper text transferprotocol) “post” based data transfer; such a request may exceed anallowable time period for an http session; such a request may requireserver processing time that exceeds a time-out period of the client andso forth.

Additionally, where a host organization provides parallel processing sothat transactions are fulfilled more quickly, there is a potential for asingle customer organization to submit a large request that, whenparallelized by the host organization, consumes an inordinate amount ofresources within the host organization, thus causing delays anddetrimental effects for other customer organizations utilizing the sameon-demand services.

Utilizing the systems and methods described herein, bulk transactionrequests received from customer organizations may be received in aformat that is convenient for the customer organizations and processedasynchronously, in a manner that best utilizes the availablecomputational resources of the host organization, without detrimentallyaffecting other users of the same on-demand services provided by thehost organization. With asynchronous processing, the client submits anasynchronous request, such as a bulk transaction request.

In the following description, numerous specific details are set forthsuch as examples of specific systems, languages, components, etc., inorder to provide a thorough understanding of the various embodiments. Itwill be apparent, however, to one skilled in the art that these specificdetails need not be employed to practice the disclosed embodiments. Inother instances, well known materials or methods have not been describedin detail in order to avoid unnecessarily obscuring the disclosedembodiments.

In addition to various hardware components depicted in the figures anddescribed herein, embodiments further include various operations whichare described below. The operations described in accordance with suchembodiments may be performed by hardware components or may be embodiedin machine-executable instructions, which may be used to cause ageneral-purpose or special-purpose processor programmed with theinstructions to perform the operations. Alternatively, the operationsmay be performed by a combination of hardware and software.

Embodiments also relate to a system or apparatus for performing theoperations herein. The disclosed system or apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina non-transitory computer readable storage medium, such as, but notlimited to, any type of disk including floppy disks, optical disks,CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), randomaccess memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, orany type of media suitable for storing non-transitory electronicinstructions, each coupled to a computer system bus. In one embodiment,a computer readable storage medium having instructions stored thereon,causes one or more processors within an on-demand service environmentimplementing a multi-tenant database system to perform the methods andoperations which are described herein. In another embodiment, theinstructions to perform such methods and operations are stored upon anon-transitory computer readable medium for later execution.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus nor are embodimentsdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the embodiments as described herein.

FIG. 1 illustrates an exemplary architecture 100 in which embodimentsmay operate. Architecture 100 depicts a host organization 110communicably interfaced with several customer organizations (105A, 105B,and 105C) via network 125. Within the host organization 110 is aweb-server 175, file repository 165, transaction queue 160, statisticsengine 170, load balancer 195, and a multi-tenant database system 130having a plurality of underlying hardware, software, and logic elements120 therein that implement database functionality and a code executionenvironment within the host organization 110. The hardware, software,and logic elements 120 of the multi-tenant database system 130 areseparate and distinct from a plurality of customer organizations (105A,105B, and 105C) which utilize the services provided by the hostorganization 110 by communicably interfacing to the host organization110 via network 125. In such a way, host organization 110 may implementon-demand services or cloud computing services to subscribing customerorganizations 105A-C.

In one embodiment, each of the separate and distinct customerorganizations (105A-105C) may be remotely located from the hostorganization 110 that provides on-demand services to the customerorganizations (105A-105C) via multi-tenant database system 130 executingtherein. Alternatively, one or more of the customer organizations105A-105C may be co-located with the host organization 110, such aswithin the same organization that hosts and provides the multi-tenantdatabase system 130 upon which underlying data is persistently stored,such as data provided within a bulk transaction request 115 from acustomer organization 105A-C. Where the customer organizations 105A-Care remote, host organization 110 provides remotely implemented cloudcomputing services.

In one embodiment, the hardware, software, and logic elements 120 of themulti-tenant database system 130 include at least a non-relational datastore 150 and a relational data store 155, which operate in accordancewith the hardware, software, and logic elements 120 that implement thedatabase functionality and code execution environment within the hostorganization 110.

In one embodiment, host organization 110 retrieves a bulk transactionrequest 115 from a transaction queue 160. In such an embodiment, thebulk transaction request 115 specifies a plurality of databasetransactions to be processed against the multi-tenant database system130 of the host organization 110. In such an embodiment, hostorganization 110 further determines a current computational load of themulti-tenant database system and processes a subset of the plurality ofdatabase transactions specified by the bulk transaction request 115against the multi-tenant database system 130 when the currentcomputational load is below a threshold. A bulk transaction results logis then updated based on the subset of the plurality of databasetransactions processed.

Host organization 110 may receive a variety of requests, including bulktransaction requests 115 for asynchronous processing from one or more ofthe plurality of customer organizations 105A-105C via the network 125.Incoming requests may be received at web-server 175 and may specify arequests for services from the host organization 110, such as areal-time transaction request for synchronous processing to retrieve orstore data on behalf of one of the customer organizations 105A-C or bulktransaction requests 115 specifying multiple database transactions. Forexample, web-server 175 may be responsible for receiving bulktransaction requests 115 from various customer organizations 105A-C vianetwork 125 and provide a web-based interface to an end-user clientmachine originating the bulk transaction request 115.

In one embodiment, the bulk transaction request 115 is received at thehost organization and stored in a file repository 165. The filerepository 165 may be a datastore separate from the multi-tenantdatabase system 130 configured specially for storing the received bulktransaction requests 115, such as a file system operating in conjunctionwith web-server 175. Alternatively, host organization 110 may store thereceived bulk transaction request 115 in the multi-tenant databasesystem 130 for later retrieval or within another location designated asa landing site for data associated with incoming requests.

Received bulk transaction requests 115 are queued for processing. In oneembodiment, host organization 110 inserts the bulk transaction request115 into transaction queue 160. The bulk transaction request 115 may beinserted into the transaction queue 160 among a plurality of bulktransaction requests and a plurality of real-time transaction requestsin the transaction queue 160. Transaction queue 160 may maintain a link,pointer, or reference to the data associated with the bulk transactionrequest 115 (e.g., a link pointing to corresponding data stored withinfile repository 165) rather than hosting the contents bulk transactionrequest 115 directly. Alternatively, the plurality of databasetransactions specified by a bulk transaction request 115 may be loadedinto the transaction queue 160 as a bulk transaction request 115.

In accordance with one embodiment, a plurality of real-time transactionrequests for synchronous processing within the transaction queue 160 areassigned a higher priority than the plurality of bulk transactionrequests 115 for asynchronous processing. In such an embodiment, thereal-time transaction requests are selected for processing against themulti-tenant database system 130 based on the higher priority.Correspondingly, in one embodiment, the plurality of bulk transactionrequests 115 in the transaction queue 160 are assigned a lower prioritythan the plurality of real-time transaction requests, and are selectedfor processing against the multi-tenant database system 130 based on thelower priority. In accordance with disclosed embodiments, the bulktransaction requests 115 are additionally selected and scheduled forprocessing based on determined current computational load of themulti-tenant database system 130, in addition to their designation aslower priority tasks.

For example, in one embodiment, real-time transaction requests aredesignated as higher priority compared to bulk transaction requests 115as a matter of policy. Real-time transaction requests may be thosetransactions received by the host organization 110 for processing whichadhere to a client/server request/response model in which a clientdevice (e.g., within customer organization 105A-C) submits a request andawaits a response from the host organization 110. Such policy orprioritization schemes may be implemented by, for example, a loadbalancer 195 working in conjunction with transaction queue 160 todistribute work to the multi-tenant database system 130. Alternatively,transaction queue 160 may implement the prioritization scheme and sendwork to the load balancer 195 in an order determined by the transactionqueue 160.

In accordance with prioritized processing schemes, in one embodiment thehost organization 110 receives a real-time transaction requestsubsequent to having received a bulk transaction request 115. In such anembodiment, despite the bulk transaction request 115 having beenreceived first, the host organization processes the real-timetransaction request against the multi-tenant database system beforeprocessing any part of the bulk transaction request 115 based on thehigher priority of the real-time transaction request. In such anembodiment, the host organization 110 sends a response to a clientdevice having submitted the real-time transaction request (e.g., arequestor having originated the real-time transaction request from oneof the customer organizations 105A-C). In such an embodiment, theresponse specifies a result for the real-time transaction request andfurther indicates processing of the real-time transaction request iscompleted. This out of order processing may be appropriate so as toapply the available computational resources to the work load that mostdirectly affects a perceived quality of service on behalf of thecustomer organizations 105A-C and/or an actual average response time forprocessing service requests from customer organizations 105A-C which aresubmitted with the expectation of real-time (e.g., synchronous,instantaneous or immediate) processing.

In one embodiment, sending a response to a client device havingsubmitted the bulk transaction request 115 includes sending a responsespecifying a session identifier assigned to the bulk transactionrequest, and further acknowledging the bulk transaction request isqueued for processing or queued for asynchronous processing. Forexample, although host organization 110 may respond to a client havingsubmitted a bulk transaction request 115, such a response does notindicate that the bulk transaction request 115 has completed, butinstead, provides an indication of successful receipt of such a request,and provides information to the client device which enables the customerorganization 105A-C to check for appropriate status at a later time orto retrieve a bulk transaction results log describing the results of theplurality of database transactions incorporated within the bulktransaction request 115.

In one embodiment, the host organization validates the bulk transactionrequest 115 against one or more specifications. For example, validatingthe bulk transaction request 115 may include a) verifying the bulktransaction request 115 complies with a maximum record count threshold;b) verifying the bulk transaction request 115 complies with a maximumsize threshold; and/or c) verifying the bulk transaction request 115complies with an accepted request format. In such an embodiment, thebulk transaction request 115 is submitted to the transaction queue 160once the bulk transaction request is successfully validated. Forexample, logic within the web-server 175 or transaction queue 160 mayapply such a validation scheme to incoming bulk transaction requests.

The one or more specifications or requirements applied against incomingbulk transaction requests 115 may be based on policy, systemperformance, or system limitations. For example, where such requests aresubmitted over http, there are size limitations which are inherent tohttp post based transactions, and thus, limit the overall size that maybe accommodated for any given request presented to the hostorganization. Accordingly, the host organization (e.g., via web-server175) may reject bulk transaction requests 115 in excess of a specifiedsize, such as 10 megabytes. Accepted formats may similarly be specified.For example, the host organization 110 may specify that it will rejectany bulk transaction request 115 that is not presented in one of severalenumerated formats, such as an XML (eXtended Markup Language) based flatfile, a CSV (Comma Separated Values) based flat file, a specified objecttype, and so forth. Additionally, the host organization 110 may specifya maximum number of records or a maximum number of database transactionsthat are acceptable within a bulk transaction request 115. For example,the host organization may specify a 10,000 record or transaction limitper bulk transaction request 115, or a 20,000 or 30,000 limitation basedon policy, system performance, or other considerations.

In some embodiments, one set of specifications are applied to bulktransaction requests 115 received at web-server 175 via http transferprotocol, while a different set of specifications is applied to bulktransaction requests 115 received via alternative transfer protocols(e.g., via a File Transfer Protocol (FTP), etc.).

In some embodiments, validation is performed via host organization 110while in alternative embodiments, validation of bulk transactionrequests 115 is performed via a client device at therequesting/submitting customer organization 105A-C, for example, vialogic downloaded locally to the client from the host organization or viaa client side interface of a customer organization 105A-C linking tocorresponding API (Application Programming Interface) logic at the hostorganization 110.

In accordance with one embodiment, the bulk transaction request 115 is abulk record upload request in which each of the plurality of individualdatabase transactions specified by the bulk transaction request includesa record and/or row to be uploaded to a table in the multi-tenantdatabase system. For example, the entire bulk transaction request 115may constitute a large data upload or a data dump from a customerorganization 105A-C to the host organization's 110 multi-tenant databasesystem 130 in which all of the database transactions specified by thebulk transaction request 115 are record adds or record inserts, eachindividual database transaction specifying all the requisite data fieldsrequired to populate one row within a table.

Alternatively, each of the plurality of database transactions specifiedby the bulk transaction request 115 may include a database transactionof varying types. For example, allowable transaction types may includeadds, updates, or deletes. Processing numerous updates and/or deletesmay require processing times that more appropriate for a bulktransaction request 115 rather than a real-time processing request.Deletes and/or updates may be simple, for example, specifying a tableand a primary key to transact against, or may be more complex, forexample, specifying a “WHERE” clause to select an appropriate record orappropriate records to transact against, potentially requiring more timeconsuming full table scans or corresponding references to index tablesand associated non-indexed tables to complete a delete or an update.

In one embodiment, the bulk transaction request 115 specifies a) a namedtable within the multi-tenant database system 130 against which toprocess the respective database transaction based on the transactiontype and b) provides or specifies transaction data to be added, updated,or selected for deletion based on the transaction type during therespective database transaction.

FIG. 2 illustrates an alternative exemplary architecture 200 in whichembodiments may operate.

In accordance with the described embodiments, work associated with bulktransaction requests 250 is applied, processed, or transacted againstthe multi-tenant database system 130 based, at least in part, on thecurrent computational load of the multi-tenant database system 130.

Taking the current computational load of the multi-tenant databasesystem into account may permit improved overall system performance andincreased flexibility to the host organization 110. For example, theoperators of host organization 110 implementing the on-demand servicesmay be sensitive to how subscribers, such as customer organizations105A-C, perceive the quality and capabilities of the on-demand servicesprovided. Customer organizations may assess the quality and capabilitiesof the on-demand services is based on system responsiveness (e.g.,response time or delay associated with processing a request for servicesand receiving a result) and also convenience. Some requests, such as asimple data search or data retrieval may be submitted by an end-user viaa client side interface in which the end-user awaits a correspondingresult/response from the host organization 110. In such a scenario, along delay may be interpreted as poor service quality.

Conversely, bulk transaction requests 250 may be submitted as part of alarge data upload or data transfer. In such a scenario, an end-userresponsible for such a request may value the convenience of submittingand managing such a request over any subjective assessment of how longsuch a request should take. For example, a database administratorcoordinating a large data upload may place a great value on the abilityto upload a bulk of database transactions rather than having to developa systematic process for uploading many thousands or even millions ofindividual records to the multi-tenant database system 130 as individualdatabase add transactions.

The ability to schedule work, such as the many database transactionsspecified in a bulk transaction request 250, based on current systemperformance and current computational load may therefore enable the hostorganization to emphasize processing resources for time sensitivetransactions (e.g., real-time transaction requests) while accommodatingthe convenience of submitting other transactions in bulk. Schedulingwork in such a way may further enable the host organization to negatepotentially negative effects associated with receiving bulktransactions. For example, immediately processing a bulk transactionrequest 250 when the multi-tenant database system 130 is operating athigh computational loads may cause all transactions, including timesensitive real-time transaction requests, to experience unacceptabledelay, thus deteriorating perceived quality levels on the part ofcustomer organizations 105A-C.

Therefore, in accordance with described embodiments, determining acurrent computational load of the multi-tenant database system 130includes retrieving one or more operational statistics from themulti-tenant database system 130 upon which to make an assessment. Forexample, determining the current computational load may be performed bythe statistics engine 170 or by a load balancer 195 operating within thehost organization 110. Similarly, the host organization 110 may computeoperational loads on an ongoing basis and store appropriate informationso that current operational loads may be retrieved as needed, forexample, by the transaction queue 160 or by a load balancer 195 seekingto schedule work.

In accordance with one embodiment, the one or more operationalstatistics upon which a current operational load is determined includes:operating statistics describing Input/Output utilization of themulti-tenant database system 130; CPU utilization of the multi-tenantdatabase system; number of free server nodes 220 available forprocessing database transactions within a pool of server nodes 290;number of active threads currently processing database transactionsagainst the multi-tenant database system; current queue time ofreal-time database transactions to be processed against the multi-tenantdatabase system; and number of queued real-time database transactions tobe processed against the multi-tenant database system.

The host organization 110 may consider any number of operationalstatistics in determining a current operational load for themulti-tenant database system 130. The determined current operationalload may result in a binary result, such as “available” for processingbulk transaction requests 250 or “not available” for processing bulktransaction requests 250, or may result in a numeric or percentage basedvalue. For example, where all nodes 220 within the server pool 290 arein a non-idle state or have at least one active work thread assigned tothem, the host organization may determine the current computational loadto be “not available” for processing bulk transaction requests.Accordingly, such requests pending in the transaction queue 160 will bedelayed or simply not scheduled for processing at that time.

Alternatively, a current computational load may be calculated to be, forexample, 60% or 40%, etc., based on CPU utilization rates, I/O usage asa percentage of operational maximums, and so forth. Such data may becollected and analyzed by, for example, statistics engine 170 which thenprovides the current operational load based on its analysis.

Accordingly, in one embodiment, processing the subset of the pluralityof database transactions when the current computational load is belowthe threshold includes determining computational resources are availablefor processing bulk transaction requests 250 based on a comparison ofthe one or more operational statistics against a corresponding one ormore operational thresholds.

For example, FIG. 2 depicts a bulk transaction request 250 having beenqueued in transaction queue 160. The queued bulk transaction requestspecifies multiple database transactions 251-256. As shown, databasetransactions 251, 252, 253, and 254 are associated with a first subsetof database transactions 260 specified by the bulk transaction request250 and database transactions 255 and 256 are remaining or second subsetof database transactions 265 of the queued bulk transaction request 250.

Responsive to a determination that current computational load is below aspecified threshold, the host organization 110 (e.g., via load balancer195) retrieves a queued bulk transaction request 250 from thetransaction queue 160 for processing. For example, load balancer 195 maycall a queue handler which is responsible for selecting queued itemsfrom the transaction queue 160. Such a queue handler may be implementedvia, for example, within an Oracle™ compatible transaction queue orother queuing mechanism capable of working in conjunction with a loadbalancer 195. The load balancer may additionally specify a type of job,such as specifying that a bulk transaction request 250 is to beretrieved from the transaction queue 160 based on a determination thatthe current computational load is below an appropriate threshold.Alternatively, the load balancer 195 may request a queued transactionwhich by default will retrieve any queued real-time transaction, andspecify that a bulk transaction request 250 is only to be returned whena) there no queued real-time transaction requests and b) currentcomputational load is below a specified threshold (e.g., below 60% loadfor example).

In one embodiment, a queue handler returns a reference pointer to theplurality of individual database transactions (e.g., 251-256) associatedwith a queued bulk transaction request 250. In alternative embodiments,the queue handler returns a requested number of database transactions(251-256) associated with a queued bulk transaction request 250. Inother embodiments, the queue handler returns a subset of databasetransactions (e.g., 260 or 265) to the load balancer 195.

In accordance with one embodiment, processing a subset of the pluralityof database transactions (e.g., subset 260 or subset 265) against themulti-tenant database system 130 includes processing the plurality ofdatabase transactions 251-256 for a pre-determined period of time. Forexample, load balancer 195 may issue as many of the databasetransactions corresponding to a bulk transaction request as are able tobe processed during a specified period of time (e.g., five seconds, fiveminutes, etc.). For example, the load balancer 195 may issue individualdatabase transactions 251-256 to a single server node 220 one afteranother in serial fashion, or may issue database transactions 251-256 tomultiple server nodes 220 within the pool of server nodes 290.Alternatively, the host organization may provide multiple databasetransactions 251-256 to a particular server node 220 directing theserver node 220 to process for the specified period of time and thenrespond indicating which database transactions were processed (e.g.,subset 260 may be specified or marked as having been processed) andwhich database transactions remain as unprocessed (e.g., subset 265 mayremain as being unprocessed).

In an alternative embodiment, the load balancer 195 allocates apre-determined number of the plurality of database transactions forprocessing. For example, the load balancer 195 selects subset 260 basedon a pre-determined number of transactions to be issued and assigns thesubset of database transactions 260 to a server node 220 which thenprocesses all of the subset of database transactions 260 without regardto processing time. While the subsets of database transactions depictedis small (e.g., four such transactions in subset 260 and two suchtransactions in subset 265), the number of transactions selected andissued for processing may be orders of magnitude larger in practice. Forexample, the multi-tenant database system 130 hosts data associated withmultiple distinct customer organizations 105A-C and thus, has processingcapacity to deal with peak loads. In non-peak times, that capacity maybe applied against bulk transaction requests 250 in which case manydatabase transactions (e.g., thousands or tens of thousands) may beprocessed quickly and efficiently by leveraging excess capacity withoutdetrimentally affecting time-sensitive transactions occurring inparallel (including time-sensitive real-time transactions that arerequested during non-peak periods). During peak load periods, it may benot be feasible to conduct any processing of asynchronous type bulktransaction requests 250 as all available resources (determined based oncurrent computational load) are being applied to other work.

In such embodiments where less than all database transactions associatedwith a bulk transaction request 250 are processed (e.g., subset 260completes leaving subset 265 as unprocessed), the host organizationre-queues the bulk transaction request 250 in the transaction queue 160.The re-queued bulk transaction request 250 thus has a subset (e.g., 260)of the plurality of database transactions 251-256 processed and furtherhas a remaining portion/subset (e.g., 265) of the plurality of databasetransactions 251-256 unprocessed. For example, the curved dashed arrowsof FIG. 2 depict a bulk transaction request being retrieved from thetransaction queue 160, being partially processed against themulti-tenant database system 130 via the server pool 290, andsubsequently re-queued in the transaction queue 160 as requiring furtherprocessing.

In accordance with described embodiments, the host organization 110updates a bulk transaction results log 270 based on the subset of theplurality of database transactions (e.g., 260 or 265) processed. Thebulk transaction results log 270 may be stored in file repository 165 orhosted within the multi-tenant database system 130. In accordance withone embodiment, the updated bulk transaction results log 270 includes atransaction result for each of the subset of database transactions(e.g., 260 or 265) processed. For example, each database transactionprocessed may be written to the bulk transaction results log 270 alongwith a completion code (e.g., pass/fail or “0” for a pass and a non-zerocode indicating a failure mode, etc.).

In accordance with one embodiment, the contents of the updated bulktransaction results log 270 are transmitted to a customer organization(e.g., one of 105A-C) responsive to a request soliciting the bulktransaction results log 270. For example, an end-user may retrieve thelog in the process of monitoring the progress of the bulk transactionrequest 250 or the end-user may retrieve the log to perform erroranalysis on any database transactions 251-256 that triggered a failureor error code (e.g., due to malformed data, improper data type, nullvalues, incorrect query syntax, etc.).

In accordance with one embodiment, host organization 110 issues a jobstatus 285 for the bulk transaction request 250. For example, job status285 may be updated and/or issued each time a portion or a subset of thedatabase transactions (260 or 265) are processed. Job status 285 mayprovide summary type information rather than detailed and individualizedtransaction by transaction information, such as that which is includedin the bulk transaction results log 270. For example, issuing a jobstatus 285 for a corresponding bulk transaction request 250 may includeindicating one or more of: completion status; queue status, percentagecomplete, number of records transacted, number of records successfullytransacted, number of transaction errors; total aggregate queue time;total aggregate processing time; and estimated time to completion. Suchjob status 285 may be stored in multi-tenant database system 130 so thatit is easily locatable and retrievable by the host organization 110 whenrequested. The job status 285 may alternatively be written to, forexample, file repository 165 or cached within a global caching layer ofthe host organization for fast accessibility without having to query themulti-tenant database system 130.

In one embodiment job status information 285 is returned to a customerorganization 105A-C responsive to a status request from the customerorganization identifying a bulk transaction request 250 submittedpreviously. For example, because the customer organizations 105A-Csubmit the bulk transaction requests 250 and receive, for example, onlyan acknowledgement of successful receipt or perhaps an indication thatthe request is queued, the customer organization may subsequently submita status request to the host organization 110 soliciting the latest jobstatus information 285 regarding the previously submitted bulktransaction request 250.

The architecture 200 depicted enables host organization 110 toiteratively retrieve a bulk transaction request 250, process portions ofthe bulk transaction request (e.g., subset 260 or 265), re-queue thebulk transaction request 250, and then continuously loop through such aprocess until all database transactions specified by a bulk transactionrequest have been processed against the multi-tenant database system130.

Thus, in accordance with one embodiment, the host organization 110(e.g., via a load balancer 195) re-retrieves the bulk transactionrequest 250 from the transaction queue (e.g., as a second, third, forthiteration, etc.), re-determines the current computational load of themulti-tenant database system 130, processes a second subset of theplurality of database transactions (e.g., processes subset 265 wheresubset 260 was processed on a prior iteration and where the secondsubset 265 is non-overlapping with the first subset 260 of the pluralityof database transactions) as specified by the bulk transaction request250 by applying or transacting the second subset of databasetransactions against the multi-tenant database system 130 when thecurrent computational load is below a threshold. Such subsequentiterations may further include a re-updating of the bulk transactionresults log 270 based on the second subset 265 of the plurality ofdatabase transactions processed and issuing a job status 285 for thebulk transaction request 250 reflecting the latest or most up-to-datestatus information (e.g., updating or revising a previously issued jobstatus 285 where necessary).

In accordance with one embodiment, so as to facilitate subsequentiterations and partial processing of bulk transaction requests 250during any iteration cycle, the host organization marks each of thesubset of the plurality of database transactions (e.g., each of databasetransactions 251-254 within subset 260 or database transactions 255-256within subset 265) specified by the bulk transaction request 250 asprocessed. For example, as each individual database transaction 251-256is processed, the transaction may be flagged to indicate whether it isprocessed or not. In an alternative embodiment, processed databasetransactions are removed from the bulk transaction request thus leavingonly unprocessed transactions within the bulk transaction request.

In one embodiment, the bulk transaction request 250 is re-queued in thetransaction queue 160 based on a determination that one or more databasetransactions specified by the bulk transaction request remainunprocessed. Alternatively, the host organization 110 finalizes the bulktransaction results log 270 based on a determination that all databasetransactions specified by the bulk transaction request 250 areprocessed. For example, all database transactions are either marked orflagged as processed or are deleted from the bulk transaction request250, thus negating the need to re-queue the bulk transaction request 250for subsequent iterative processing.

In some embodiments, the host organization 110 may automaticallyinitiate an outgoing message to the requesting customer organization105A-C associated with a completed bulk transaction request indicatingthat processing is complete. Alternatively, the host organizationprovides job status information 285 responsive to a status request.

Because multiple server nodes or instances 220 are present within theserver pool 290, it may be advantageous to issue parts or subsets (e.g.,260 or 265) of a bulk transaction request in parallel for expeditedprocessing based on an evaluation of current computational load. Atother times, the current computational load may be such that it is moreappropriate to issue parts or subsets (e.g., 260 or 265) of a bulktransaction request in serial. Both may be accommodated in a dynamic andflexible manner by having distinct trigger points or multiple triggerpoints by which the host organization 110 may programmatically determineto issue work associated with bulk transaction requests 250 aggressivelyusing parallel processing or more conservatively using serial/sequentialprocessing.

Thus, in accordance with one embodiment, processing the subset of theplurality of database transactions (e.g., 260 or 265) specified by thebulk transaction request 250 against the multi-tenant database system130 when the current computational load is below the threshold includesselecting serial processing when the current computational load is belowthe threshold by a first margin, wherein serial processing comprisesissuing the subset of database transactions to one server node within apool of server nodes for processing. For example, if a specifiedthreshold at which point bulk request processing work may be distributedto the server pool 290 is, for example, 60% current computational load,a first margin of 20% for example, may dictate that only serialprocessing be selected for current computational loads of 40% up to 60%.In such an embodiment, parallel processing may therefore be selectedonly when the current computational load is below the threshold by asecond margin. Any margin greater than 20% below a specified thresholdmay therefore allow distribution of bulk transaction request workload tobe distributed to the server pool 290 in a parallel manner. Using theabove example, a current computational load of 0% up to 40% maytherefore allow for selecting parallel processing, current computationalloads of 40% up to 60% may correspond to selecting serial processing,and current computational loads in excess of 60% would delay allprocessing associated with bulk transaction requests. The abovespecified thresholds are exemplary only. Other thresholds and marginsmay be specified so as to enable a dynamic and flexible selectionmechanism between serial and parallel processing.

In accordance with one embodiment, parallel processing includes: a)segmenting the subset of database transactions (e.g., 260 or 265) into aplurality of parts, and b) issuing the plurality of parts constitutingthe subset of database transactions (e.g., 260 or 265) to a plurality ofserver nodes 220 within the pool of server nodes 290 for processing inparallel. For example, a subset of database transactions (e.g., 260)selected for parallel processing may be broken into four parts (e.g.,via load balancer 195) and then issued simultaneously to four separateserver nodes within the server pool 290, such as individual server nodes221, 222, 223, and 224, each server node 221-224 processing itsrespective part and transacting with the multi-tenant database system130 in parallel. Similarly, work may be broken into work threads andassigned to redundant instances, such as virtual machines or JavaVirtual Machines (JVMs) for multi-threaded parallel processing.

In accordance with one embodiment, bulk transaction request 250 is oneof a plurality of requests received from a plurality of customerorganizations (e.g., 105A-C). In such an embodiment, each customerorganization corresponds is one of: a separate and distinct remoteorganization, an organizational group within the host organization(e.g., such as a division or department within a business Enterprise), abusiness partner of the host organization 110, or a customerorganization that subscribes to cloud computing services provided by thehost organization 110.

Because the host organization supports multiple tenants (e.g., customerorganizations 105A-C) with the same underlying shared multi-tenantdatabase system 130 implementation, the host organization may organizebulk transaction requests 250 in such a way that resources are allocatedevenly or prevented from being consumed in an un-even manner by one ormore of the multiple customer organizations. For example, one customerorganization 105A-C submitting numerous bulk transaction requests 250may inadvertently consume more than an appropriate share ofcomputational resources of the host organization where there iscontention for resources between such bulk transaction requests (e.g.,multiple bulk transaction requests 250 from multiple customerorganizations 105A-C are queued and awaiting processing).

Thus, in accordance with one embodiment, the host organization 110receiving a second one or more bulk transaction requests 250 (e.g.,within the file repository 165 of the host organization 110)responsively associates the bulk transaction request 250 and the secondone or more additional bulk transaction requests with one of a pluralitycustomer organizations (105A-C) based on an Organization ID (OrgID)and/or a User ID (UserID) accompanying each bulk transaction request250. For example, such an OrgID or UserID may uniquely identify acustomer organization 105A-C so that any number of received bulktransaction requests 250 from a single customer organization 105A-C,from end users of a single customer organization, or from client devicesassociated with a particular customer organization may appropriately belinked to the customer organization for whom work is being performed.

Thus, in accordance with one embodiment, a job session is instantiatedon behalf of any customer organization 105A-C having one or more bulktransaction requests 250 received by the host organization 110. In someembodiments, a customer organization requests a job session to beinstantiated and then submits bulk transaction requests 250 into the jobsession. In other embodiments, job session is instantiated automaticallyand bulk transaction requests 250 are associated with a job sessionbased on the OrgID and/or UserID accompanying such requests. In such away, host organization 110 may ensure evenly distributed processingopportunities for each customer organization 105A-C. Where desirable,multiple job sessions may be allowed for select customer organizations105A-C, thus allowing preferential processing of submitted bulktransaction requests 250.

In accordance with some embodiments, all received bulk transactionrequests 250 are loaded into the transaction queue 160 and retrieving abulk transaction request 250 from the transaction queue 160 is performedon a round robin scheduling basis, selecting one bulk transactionrequest from among all bulk transaction requests in the transactionqueue at a time. Where job sessions are utilized for grouping suchrequest, retrieving a bulk transaction request 250 from the transactionqueue 160 is performed by first selecting one of the instantiated jobsessions on a round-robin basis and then retrieving a bulk transactionrequests 250 associated with the selected job session (e.g., on a FIFO(first in first out) basis, on a round-robin basis, etc.).

FIG. 3 shows a diagrammatic representation of a system 300 in whichembodiments may operate, be installed, integrated, or configured.

In one embodiment, system 300 includes a memory 395 and a processor orprocessors 390. For example, memory 395 may store instructions to beexecuted and processor(s) 390 may execute such instructions. System 300includes bus 315 to transfer transactions and data within system 300among a plurality of peripheral devices communicably interfaced with bus315. System 300 further includes web-server 325, for example, to receiverequests, return responses, and otherwise interface with remote clients,such as client devices located within customer organizations 105A-C.

System 300 is further depicted as having a statistics engine 335designed to collect, aggregate, and process operational statisticsassociated with a communicatively interfaced multi-tenant databasesystem (such as that depicted at element 130 of FIG. 1) and optionallyto calculate a current operational load of the multi-tenant databasesystem. File repository 330 receives and stores bulk transactionrequests submitted to system 300, such as bulk transaction requestsawaiting processing. Transaction queue 345 queues a plurality ofrequests awaiting processing on behalf of users of the multi-tenantdatabase system; such requests include bulk transaction requests andreal-time transaction requests pending processing against themulti-tenant database system. System 300 further includes a globalcaching layer 350 to provide caching services to communicably interfaceddevices and systems and in particular, provide caching of statusinformation and results data (e.g., meta data, etc.).

Distinct within system 300 is hardware based load balancer 301 whichincludes transaction retriever 370, load analyzer 375, results module380, and distribution module 385. In accordance with one embodiment,transaction retriever 370 retrieves database transactions for processingfrom the transaction queue 345 including retrieving bulk transactionrequests and real-time transaction requests for processing. Loadanalyzer 375 retrieves calculated current computational loads (e.g.,from statistics engine 335) or retrieves information necessary tocalculate and determine a current computational load of the multi-tenantdatabase system. In some embodiments, load analyzer 375 further selectsa method of processing, including making a determination to scheduledatabase transactions within a bulk transaction request in serial orparallel. Distribution module 385 operates in conjunction with loadanalyzer 375 to distribute work to available server nodes within aserver pool based on information or directives provided by load analyzer375. Results module 380 collects results and exit codes and updates abulk transaction results log based on the collected information.

FIG. 4 is a flow diagram illustrating a method 400 for bulk uploading ofdata in an on-demand service environment in accordance with oneembodiment, including receiving, managing, and processing bulktransaction requests against a multi-tenant database system based on acurrent computational load of such a system. Method 400 may be performedby processing logic that may include hardware (e.g., circuitry,dedicated logic, programmable logic, microcode, etc.), software (e.g.,instructions run on a processing device to perform various queryoperations such reading, writing, updating, and searching a multi-tenantdatabase system, or a combination thereof. In one embodiment, method 400is performed by hardware logic, such as the hardware based load balancerdepicted at element 301 of FIG. 3. Some of the blocks and/or operationslisted below are optional in accordance with certain embodiments. Thenumbering of the blocks presented is for the sake of clarity and is notintended to prescribe an order of operations in which the various blocksmust occur.

Method 400 begins with processing logic receiving a bulk transactionrequest at a host organization, the bulk transaction request specifyinga plurality of database transactions to be processed against amulti-tenant database system of the host organization (block 405). Atblock 410, processing logic validates the bulk transaction requestagainst one or more specifications and at block 415, processing logicinserts the bulk transaction request into a transaction queue.

At block 420, processing logic determines a current computational loadof the multi-tenant database system. At block 425, processing logicretrieves a bulk transaction request from the transaction queue. Atblock 430, processing logic processes a subset of the plurality ofdatabase transactions specified by the bulk transaction request based onthe current computational load. Alternatively, processing logic maydelay processing of the bulk transaction request based on the currentcomputational load.

At block 435, processing logic updates a bulk transaction results logbased on the subset of the plurality of database transactions processedand at block 440, processing logic of the host organization issues a jobstatus for the bulk transaction request indicating completion status(e.g., partially complete, percentage complete, all transactionscomplete, etc.).

At block 445, processing logic re-queues the bulk transaction request inthe transaction queue having the subset of the plurality of databasetransactions processed and having a remaining portion of the pluralityof database transactions unprocessed.

At block 450, processing logic iteratively repeats method operations asnecessary until processing of the bulk transaction request is complete.For example, the method may re-retrieve a partially processed bulktransaction request from the transaction queue, process all of aremaining portion or part of the remaining portion based on are-determined current computational load, etc.

FIG. 5 illustrates a diagrammatic representation of a machine 500 in theexemplary form of a computer system, in accordance with one embodiment,within which a set of instructions, for causing the machine 500 toperform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine may be connected(e.g., networked) to other machines in a Local Area Network (LAN), anintranet, an extranet, or the Internet. The machine may operate in thecapacity of a server or a client machine in a client-server networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment or as a server or series of servers within anon-demand service environment, including an on-demand environmentproviding multi-tenant database storage services. Certain embodiments ofthe machine may be in the form of a personal computer (PC), a tablet PC,a set-top box (STB), a Personal Digital Assistant (PDA), a cellulartelephone, a web appliance, a server, a network router, switch orbridge, computing system, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines (e.g., computers) that individually or jointly execute a set(or multiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 500 includes a processor 502, a mainmemory 504 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc., static memory such as flash memory, static random accessmemory (SRAM), volatile but high-data rate RAM, etc.), and a secondarymemory 518 (e.g., a persistent storage device including hard disk drivesand persistent multi-tenant database implementations), which communicatewith each other via a bus 530. Main memory 504 includes transactionqueue 524 (e.g., queues and manages multiple pending requests includingbulk transaction requests and real-time transaction requests pendingprocessing against a communicatively interfaced multi-tenant databasesystem). Also within main memory 504 is global cache layer 523 whichcaches data, metadata, transaction status, etc., on behalf of connectedcomponents. Main memory 504 and its sub-elements (e.g. 523 and 524) areoperable in conjunction with processing logic 526 and processor 502 toperform the methodologies discussed herein. Hardware based load balancer534 operates in conjunction with processing logic 526 and processor 502to retrieve pending transaction requests from transaction queue 524 forprocessing against a connected multi-tenant database system.

Processor 502 represents one or more general-purpose processing devicessuch as a microprocessor, central processing unit, or the like. Moreparticularly, the processor 502 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processor 502 may alsobe one or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. Processor 502 is configured to execute the processing logic 526for performing the operations and functionality which is discussedherein.

The computer system 500 may further include a network interface card508. The computer system 500 also may include a user interface 510 (suchas a video display unit, a liquid crystal display (LCD), or a cathoderay tube (CRT)), an alphanumeric input device 512 (e.g., a keyboard), acursor control device 514 (e.g., a mouse), and a signal generationdevice 516 (e.g., an integrated speaker). The computer system 500 mayfurther include peripheral device 536 (e.g., wireless or wiredcommunication devices, memory devices, storage devices, audio processingdevices, video processing devices, etc.

The secondary memory 518 may include a non-transitory machine-readablestorage medium (or more specifically a non-transitory machine-accessiblestorage medium) 531 on which is stored one or more sets of instructions(e.g., software 522) embodying any one or more of the methodologies orfunctions described herein. The software 522 may also reside, completelyor at least partially, within the main memory 504 and/or within theprocessor 502 during execution thereof by the computer system 500, themain memory 504 and the processor 502 also constituting machine-readablestorage media. The software 522 may further be transmitted or receivedover a network 520 via the network interface card 508.

While the subject matter disclosed herein has been described by way ofexample and in terms of the specific embodiments, it is to be understoodthat the claimed embodiments are not limited to the explicitlyenumerated embodiments disclosed. To the contrary, the disclosure isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements. It is tobe understood that the above description is intended to be illustrative,and not restrictive. Many other embodiments will be apparent to those ofskill in the art upon reading and understanding the above description.The scope of the disclosed subject matter is therefore to be determinedin reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

What is claimed is:
 1. A method in a host organization having at least aprocessor and a memory therein, wherein the method comprises: receivinga bulk transaction request from a client device communicativelyinterfaced to the host organization at a web-server interface of thehost organization executing via the processor and memory of the hostorganization, wherein the bulk transaction request specifies a pluralityof database transactions to be processed against a database system ofthe host organization; sending a response to the client device havingsubmitted the bulk transaction request from the web-server interface ofthe host organization, wherein the response provides at least: (a) anindication of successful receipt of the bulk transaction request and (b)an acknowledgement that the bulk transaction request is queued forprocessing or queued for asynchronous processing; determining a currentcomputational load of the database system based on a plurality ofreal-time transaction requests and a plurality of bulk transactionrequests awaiting processing via the database system; and processing asubset of the plurality of database transactions specified by the bulktransaction request against the database system when the currentcomputational load is below a threshold, wherein the plurality ofreal-time transaction requests are assigned a higher priority than theplurality of bulk transaction requests and are selected for processingagainst the database system based on the higher priority and furtherwherein the plurality of bulk transaction requests are assigned a lowerpriority than the plurality of real-time transaction requests and areselected for processing against the database system based on the lowerpriority and based further on the determined current computational loadof the database system.
 2. The method of claim 1, further comprising:inserting the bulk transaction request into a transaction queue among aplurality of bulk transaction requests and a plurality of real-timetransaction requests in the transaction queue.
 3. The method of claim 2,wherein: processing the subset of the plurality of database transactionsleaves a remaining portion of the plurality of database transactionsunprocessed; and wherein the method further comprises: updating a bulktransaction results log based on the subset of the plurality of databasetransactions processed and the remaining portion of the plurality ofdatabase transactions unprocessed; re-queuing the bulk transactionrequest specifying the remaining portion of the plurality of databasetransactions unprocessed in the transaction queue for later processing.4. The method of claim 1, further comprising: sending a response to aclient device having submitted the bulk transaction request, wherein theresponse specifies a session identifier assigned to the bulk transactionrequest, and further wherein the response acknowledges the bulktransaction request is queued for asynchronous processing.
 5. The methodof claim 1, further comprising: receiving a real-time transactionrequest at the host organization subsequent to receiving the bulktransaction request; processing the real-time transaction requestagainst the database system before processing any part of the bulktransaction request based on the higher priority of the real-timetransaction request; and sending a response to a client device havingsubmitted the real-time transaction request, wherein the responsespecifies a result for the real-time transaction request and furtherwherein the response indicates synchronous processing of the real-timetransaction request is complete.
 6. The method of claim 1, furthercomprising: validating the bulk transaction request at the hostorganization against one or more specifications.
 7. The method of claim6, wherein: validating the bulk transaction request comprises: verifyingthe bulk transaction request complies with a maximum record countthreshold, verifying the bulk transaction request complies with amaximum size threshold, verifying the bulk transaction request complieswith an accepted request format; and wherein the method furthercomprises: submitting the bulk transaction request to the transactionqueue when the bulk transaction request is successfully validated. 8.The method of claim 1: wherein the bulk transaction request comprises abulk record upload request; and wherein each of the plurality ofdatabase transactions specified by the bulk transaction requestcomprises a record and/or row to be uploaded to a table within thedatabase system.
 9. The method of claim 1, wherein each of the pluralityof database transactions specified by the bulk transaction requestcomprises: a transaction type selected from add, update, or delete; anamed table within the database system against which to process therespective database transaction based on the transaction type; andtransaction data to be added, updated, or selected for deletion based onthe transaction type during the respective database transaction.
 10. Themethod of claim 1, wherein determining the current computational load ofthe database system comprises: retrieving one or more operationalstatistics from the database system, each operating statistic describingInput/Output utilization of the database system; CPU utilization of thedatabase system; number of free server nodes available for processingdatabase transactions within a pool of server nodes; number of activethreads currently processing database transactions against the databasesystem; current queue time of real-time database transactions to beprocessed against the database system; and number of queued real-timedatabase transactions to be processed against the database system.